fix(evidence): refresh the pending release-evidence digest - #39
Merged
Conversation
Two commits landed after the one whose content the bundle recorded, so release-evidence.module.setup_digest no longer matched the module and emit_evidence.py --check failed. That check is a required status check in nddev-harnesses, so it blocked every pull request there, including unrelated documentation ones. Re-emit with --pending: the bundle was already pending with zero lane records, and it stays pending. No approval is claimed and no lane record is fabricated — promotion still requires real CI lane executions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
release-evidence.module.setup_digestrecorded the module content as of an older commit; two commits landed after it, soemit_evidence.py --checkreported a mismatch. That check is a required status check innddev-harnesses, so it blocked every pull request there — including unrelated documentation ones — since 2026-07-26.Re-emitted with
--pending. The bundle was alreadypendingwith zero lane records and stayspending: no approval is claimed and no lane record is fabricated, so promotion still requires real CI lane executions.harness.commitis bound tonddev-harnessesmain(9f26a2f4…).emit_evidence.py --checknow passes:release-evidence bundle is valid (decision: pending).